System and Method for Smart Graphical Components

ABSTRACT

A system and method in which a graphical component determines its appearance and runtime behavior based upon the type of container to which it belongs is provided. The container type corresponds to an implementation construct such as a class in C++ and Java, or a struct in C. This implementation construct is referred to as the classtype. The graphical component determines the classtype of it&#39;s parent container at runtime and dynamically alters its appearance and behavior based upon a programmatic heuristic or a configuration file. For example, a smart graphical component placed inside of a container with a classtype of “desktop” may display descriptive text, however, the same component may not display the descriptive text when in a toolbar. Runtime behavior may also be determined based upon the classtype of the parent container. Component behavior resulting from user activation can also vary depending upon the parent container classtype.

RELATED APPLICATIONS

This application is a Continuation of U.S. Patent Application US2004/0113951, Ser. No. 10/322,099, filed on Dec. 17, 2002 titled “Systemand Method for Smart Graphical Components.”

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates in general to a system and method ofproviding smart graphical components. In particular, the presentinvention provides components that automatically determine theappearance and behavior characteristics.

2. Description of the Related Art

Today's computing environment is dominated by graphical user interfaces(GUIs). GUIs contain various graphical components, or widgets, thatperform an array of different functions. For example, an icon is acommon graphical component that usually consists of an image and somedescriptive text. When an icon is activated (clicked, invoked, selected,etc.) it will typically launch an application or another graphicalcomponent that provides information or exposes some set of functionalityto the user.

The facilities that are needed to create GUIs are provided by theoperating system. Such facilities usually include a method to draw tothe screen, process events (e.g., mouse clicks, keyboard press events,etc.), and a base set of widgets. Modern operating systems provide thesefunctions to application developers who use them to create graphicalapplications, such as Lotus Notes. Furthermore, the operating systemitself often uses these facilities to provide a desktop environment tothe user. The Microsoft Windows™ and UNIX™ operating systems haveincluded graphical facilities and a desktop environment since the 1980s.

Often times it is desireable to be able to place graphical components ofthe same type (e.g., icons) into different containers that appear on thedisplay, such as toolbars, folders, and the like. Furthermore, it may bedesirable for the component to vary it's appearance and behavior basedupon the type of container in which it is located. For example, atoolbar is typically a small container usually nested inside of a largercontainer, such as a frame or a desktop. The size of the container, suchas a toolbar, imposes size constraints on the graphical components thatare included in the container. For example, when an icon is displayedinside of a desktop it may display both an image and descriptive text.However, if the same icon is placed in a different container, such as atoolbar, the developer may not wish to display the descriptive text inorder to conserve space. Other behavior may also be different, such aswhether a border is drawn around the graphical component when the userpositions the mouse pointer over the object.

A challenge with graphical component placement is that such placement isoften configurable by the user and, therefore, not known by thedeveloper beforehand. Traditional systems address this challenge byproviding similar, but different, graphical components that are added tothe different containers. Likewise, behavior of the components intraditional systems is handled by the creation of similar, yetdifferent, components.

For example, in traditional systems a toolbar-icon is created forplacement in a toolbar while a desktop-icon is created for placement ina desktop. Developers using traditional systems and methods arechallenged by the difficulty of moving graphical components from onetype of container to another because of the different behavior andappearance attributes corresponding to the containers. What is needed,therefore, is a system and method that provides “smart” graphicalcomponents that detect their parent container type at runtime and adjusttheir behavior and appearance accordingly. What is further needed is away to provide “smart” graphical components programmatically with codeincluded with the component or through the use of a configuration filethat is read and processed by the graphical component.

SUMMARY

It has been discovered that the aforementioned challenges are resolvedusing a system and method in which a graphical component determines it'sappearance and behavior at runtime based upon the type of container towhich it belongs.

The actual container type corresponds to an implementation constructsuch as a class in C++ and Java or a struct in C. This implementationconstruct will be referred to as the classtype. The smart componentattempts to determine the classtype of it's parent component (e.g., acontainer) at runtime. If the identified classtype is of a type that thecomponent recognizes, the component modifies its behavior and appearanceaccording to the identified classtype. The behavior and appearancemodifications can be programmatically incorporated into the smartcomponent or read from a configuration file. If the classtype of theparent is not recognized, the component may be programmed to ascend it'sparent hierarchy until a recognized container is found. In this manner,the component may be placed inside of a container with an unknownclasstype, but if the parent container is itself inside of anothercontainer with a known classtype, then the component can configureitself as if it had been placed directly in the known containerclasstype.

The appearance and behavior of the smart component is determined by theclasstype of it's parent container. For example, a smart icon willdisplay a text description if it's parent classtype is a desktop.However, the same smart icon will not display the text description ifit's parent classtype is a toolbar. Furthermore, the smart iconsbehavior may differ depending on the type of parent container. Forexample, if the icond is placed in a toolbar it may be programmed todraw a border around itself when the user places the mouse pointer overit. However, if the same icon is placed on the desktop it may beprogrammed to not display a border when the pointer passes over it. Inaddition, the smart icon may be programmed to execute different coderelated to the component upon activation depending upon the type ofcontainer to which it belongs.

The foregoing is a summary and thus contains, by necessity,simplifications, generalizations, and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the present invention, asdefined solely by the claims, will become apparent in the non-limitingdetailed description set forth below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerousobjects, features, and advantages made apparent to those skilled in theart by referencing the accompanying drawings. The use of the samereference symbols in different drawings indicates similar or identicalitems.

FIG. 1 is a network diagram of a computer system using self-containeddesktops;

FIG. 2 is a block diagram of components included in providingself-contained desktops;

FIG. 3 is a high level flowchart showing administrator steps taken toprovide self-contained desktops;

FIG. 4 is a flowchart showing administrator steps taken to set up aparticular site;

FIG. 5 is a flowchart showing administrator steps taken to set up auser;

FIG. 6 is a flowchart showing administrator steps taken to set up aworkstation;

FIG. 7 is a flowchart showing administrator steps taken to set upapplication extensions;

FIG. 8 is a flowchart showing administrator steps taken to set upapplication references;

FIG. 9 is a flowchart showing administrator steps taken to createself-contained desktops;

FIG. 10 is a flowchart showing steps taken by a server to deliverself-contained desktops to a client;

FIG. 11 is a screen layout of a screen used by an administrator to setup a new site;

FIG. 12 is a screen layout of a screen used by an administrator tomanage desktops and machines for a given site;

FIG. 13 is a screen layout of a screen used by an administrator to setup a new user;

FIG. 14 is a screen layout of a screen used by an administrator to setup an application that is available as a component within one or moreself-contained desktops;

FIG. 15 is a screen layout of a screen used by an administrator to setup native applications;

FIG. 16 is a screen layout of a screen used by an administrator tomanage workstations;

FIG. 17 is a flowchart showing steps taken to distribute self-containeddesktops to servers;

FIG. 18 is a flowchart showing steps taken to distribute self-containeddesktops from a server to a client;

FIG. 19 is a flowchart showing steps taken to create custom applicationextensions;

FIG. 20 is a flowchart showing an application extension lifecycle;

FIG. 21A is a block diagram showing components and resources beingdistributed from an administrator to multiple clients;

FIG. 21B is a block diagram showing components and resources beingrecovered by an administrator from servers following a data loss by theadministrator;

FIG. 22 is a flowchart showing steps taken by an administrator indistributing self-contained desktops and subsequently recoveringself-contained desktops from servers following a disaster event;

FIG. 23 is a flowchart showing steps taken by a client to receive anddisplay desktops;

FIG. 24 is a flowchart showing steps taken by a server to providedesktop information to a client based on the user's role and theworkstation's role;

FIG. 25 is a block diagram showing processing performed by a server andinteraction between the server, clients, and administrator;

FIG. 26 is a flowchart showing steps taken by a client in initializingand displaying self-contained desktops;

FIG. 27 is a screen layout of a sample desktop displayed on a clientworkstation along with a pop-up menu of other self-contained desktopsavailable to the client;

FIG. 28A is a hierarchy chart of directories used by the client shell indisplaying and managing desktops;

FIG. 28B is a hierarchy chart of sections included with the shellconfiguration file;

FIG. 28C is a hierarchy chart of objects included in the self-containeddesktop file;

FIG. 29 is a flowchart showing steps taken to initialize the client touse self-contained desktops;

FIG. 30 is a flowchart showing steps taken during client initialization;

FIG. 31 is a flowchart showing steps taken during native operatingsystem login;

FIG. 32 is a flowchart showing steps taken when invoking the Java shelllauncher;

FIG. 33A is a screen layout showing an example of a smart graphicalcomponent;

FIG. 33B is a screen layout showing an second example of a smartgraphical component;

FIG. 34 is a hierarchy chart showing various desktop objects;

FIG. 35 is a flowchart showing steps taken in initializing smartgraphical components;

FIG. 36 is a flowchart showing steps taken in processing displayattributes for smart graphical components;

FIG. 37 is a flowchart showing steps taken in processing behaviorattributes for smart graphical components; and

FIG. 38 is a block diagram of an information handling system capable ofimplementing the present invention.

DETAILED DESCRIPTION

The following is intended to provide a detailed description of anexample of the invention and should not be taken to be limiting of theinvention itself. Rather, any number of variations may fall within thescope of the invention which is defined in the claims following thedescription.

FIG. 1 is a network diagram of a networked computer system that usesself-contained desktops. Administrator 100 creates self-containeddesktops 110 by combining images 115, application extensions 120,national language translations 125, client configuration files 130,server configuration files 135, and desktop profile information 140.Self-contained desktops 110 include all information needed for a clientto use components on the client's workstation given the client'sparticular role.

Self-contained desktops 110 are transmitted to one or more servers 150for dissemination to clients. Servers 150 combine user roles 155 withworkstation roles 160 to determine which self-contained desktops to sendto clients. Clients 165 perform login function 170 during which the userID, and password are gathered and transmitted to servers 150 toeffectuate a login. Clients 165 perform login function 170 during whichthe user ID and machine ID are gathered and transmitted to servers 150to receive a list of allowed desktops.

Servers 150 receive the user ID, password, and machine ID from clientsand determine which self-contained desktops to transmit to the clientsbased upon the user roles 155 and the workstation roles 160 thatcorrespond to the particular user ID and the particular workstationbeing used by the client. The identified self-contained desktops areresponsively transmitted from server 150 to client 165.

Client 165 performs load shell process 175 to load shell application 180onto the client workstation. The shell process is an application that isloaded onto a middleware application, such as a Java virtual machine(JVM). In this manner, the shell application appears consistent andsubstantially similar regardless of the operating system platform beingused by the client workstation. Shell application 180 is adapted toretrieve and display self-contained desktops 190. Client 165 receivesself-contained desktops based upon the intersection of the user and theworkstation identifiers. The self-contained desktops are received anddisplayed using process 185. A given client can therefore utilizemultiple self-contained desktops. These self-contained desktops includetoolbars, menus, and other graphical user interface items used tocommunicate with the user. Some of these user interfaces includefunctionality that communicate with server applications hosted byservers 150. Other user interfaces include extensions that map toclient-based applications 195. When a user clicks on a desktop componentthat maps to a client-based application, functionality exists within theself-contained desktop to invoke, or otherwise use, the client-basedapplication. If a client has multiple self-contained desktops at itsdisposal, the user can switch between the various self-containeddesktops by using a menu provided by shell application 180. For example,in a banking environment if a user is both a loan officer and a branchmanager both of the corresponding self-contained desktops for theseroles would be loaded into shell 180 provided that the workstation iscapable of performing both of these roles. To perform loan officerfunctions, the user selects the loan officer desktop from shellapplication 180. Likewise, to perform branch manager functions, the userselects the branch manager desktop from shell application 180. Inaddition, a default role can be provided so that the initially displayeddesktop corresponds to the user's primary, or default, role.

FIG. 2 is a block diagram of components included in providingself-contained desktops. Administrator 200 defines a topology, userdefinitions, site definitions, and desktop definitions. Administrator200 defines a topology by providing workstation definitions 205.Workstation definitions 205 include workstation addresses 210 andallowed desktops 215 that define which roles, or desktops, are allowedto be used on the various workstations. For example, in a bankingenvironment a workstation that is located at a teller window may havespecial equipment, such as a teller box, so that the workstation iscapable, or allowed, to perform teller functions. Another workstation,perhaps at a desk away from the teller area, may be incapable ofperforming teller functions.

User definitions 220 are used to define the users of the system and theroles such users perform. User definitions 220 include user data 225 andassigned group data 230. User data 225 includes user identifiers anduser passwords. Assigned group data 230 includes the roles a particularuser is allowed to perform. For example, a branch manager may be allowedto perform branch manager, loan officer, and teller functions while ateller may only be allowed to perform teller functions.

Site definitions 235 include information about a particular site. In abanking environment, a site may be a branch office of the bank. Sitedefinitions 235 include group desktop map 240 that provides a commondesktop for users at a particular site as well as site information 245that provides details concerning the site.

Desktop definitions 250 include components used to create self-containeddesktops that are used by clients. Desktop definitions 250 includeimages 252 that are displayed on the self-contained desktop, andapplication extensions 254 that provide details about client-basedapplications that are accessible from the self-contained desktop.Desktop definitions 250 also include resources, such as nationallanguage translations 256, so that users are able to select theresources, such as a language preference, that best fits their needs.Desktop definitions 250 also include client configurations 258 andserver configurations 260. These configurations include informationabout the components included with a particular self-contained desktop.

Administrator 200 create self-contained desktops and publishes theself-contained desktops on one or more servers 265 that are accessibleby clients. Server 265 includes persistent storage 270 andauthentication function 280. Persistent storage 270 includes user data272, topology information 274, and self-contained desktops 276. The userdata and topology data are used to determine which self-containeddesktops 276 are allowed to be used by a given client using a givenworkstation. Server 265 provides desktops which are authorized forparticular user/workstation to client 290. The self-contained desktopsare received by the client and displayed on platform independent shell295. In this manner, server 265 sends identified desktops to client 290without regard to the particular operating system platform being used bythe client.

FIG. 3 is a high level flowchart showing steps taken by theadministrator to provide self-contained desktops. Administratorprocessing commences at 300 whereupon the administrator defines users(predefined process 310, see FIG. 5 for further details). Theadministrator also defines workstations that are used by users of thesystem (predefined process 320, see FIG. 6 for further details).

Resources that are needed by clients, such as national languagetranslations, are set up so that the resources can be included inself-contained desktops (predefined process 330). Application extensionscorresponding to applications available from a workstation are defined(predefined process 340, see FIG. 7 for further details). Self-containeddesktops are packaged including all of the components needed to performa particular job role (predefined process 350, see FIG. 8 for processingdetails).

A determination is made as to whether a new site is being added(decision 360). If a new site is being added, decision 360 branches to“yes” branch 365 whereupon a new site is defined (predefined process370, see FIG. 4 for processing details). On the other hand, if a newsite is not being added decision 360 branches to “no” branch 375bypassing step 370.

The defined desktop is mapped to one or more sites and one or more roles(predefined process 380). In this manner, a single desktop can be usedat multiple sites for multiple roles. Conversely, a different desktopcan be defined and used at each site and for each role. The desktopcomponents are packaged into a self-contained desktop and theself-contained desktop is published to one or more servers fordissemination to the various clients (predefined process 390, see FIG. 9for processing details). Administrator processing ends at 395.

FIG. 4 is a flowchart showing administrator steps taken to set up aparticular site. Processing commences at 400 whereupon a uniqueidentifier is assigned to the site (step 405). A parent site isidentified for the site (step 410). For example, a branch office mayhave a regional office for a parent site. In this manner, the new sitecan inherit characteristics and attributes from the parent site so thatthe characteristics and attributes are consistent and do not have to bereentered for each site. A determination is made as to whether a parentsite was identified (decision 415). If a parent site was identified,decision 415 branches to “yes” branch 418 whereupon policies anddesktops for the parent are retrieved (step 420). On the other hand, ifthe parent site was not identified decision 415 branches to “no” branch422 whereupon the administrator sets the policies and desktops todefault values for the site (step 425).

Policies that were either retrieved or set for a particular site can bemodified according to the particular site's needs (step 430). In thismanner, a site can have slightly different policies from those of aparent site. Sites have one or more roles that are performed by usersworking at sites. In a banking environment, a branch office site mayhave roles such as a teller, a loan officer, and a branch manager. Thefirst role for the site is selected (step 435). A determination is madeas to whether the role needs to be modified (decision 440). If the roleneeds to be modified, decision 440 branches to “yes” branch 445whereupon a self-contained desktop is selected for the role (step 450).On the other hand, if the desktop does not have to be modified for therole, decision 440 branches to “no” branch 455 bypassing step 450. Inthis manner, the child site uses the same desktop as the parent site fora particular role, yet the administrator has the flexibility to assign adifferent desktop to the child site for a given role.

A determination is made as to whether there are more roles for the site(decision 460). If there are more roles, decision 460 branches to “yes”branch 465 whereupon the next role for the site is selected (step 470)and processing loops back to process the next role. This loopingcontinues until there are no more roles for the site, at which pointdecision 460 branches to “no” branch 475 whereupon the desktops andother data selected for the site are stored (step 480). Processing thenreturns at 495.

FIG. 5 is a flowchart showing steps taken by the administrator to definea new user. Processing commences at 500 whereupon a unique useridentifier, such as a user ID, is assigned to the user (step 505). Aninitial passwords is also assigned to the user (step 510). A user nameand/or description is also entered for the user (step 515). A nationallanguage preference is selected for the user (step 520).

A role is selected for the user (step 525) from a list of roles that hasbeen created by the administrator and stored in data store 530. Adetermination is made as to whether the selected role is the defaultrole for the user (decision 540). If the selected role is the defaultrole for the user, decision 540 branches to “yes” branch 545 whereuponthe selected role is assigned as the default role for the user (step550). On the other hand, if the selected role is not the default role,decision 540 branches to “no” branch 555 bypassing step 550.

A determination is made as to whether there are more roles to assign tothe user (decision 560). If there are more roles to assign to the user,decision 560 branches to “yes” branch 565 which loops back to select andprocess the next role for the user. This looping continues until thereare no more roles to assign to the user, at which point decision 560branches to “no” branch 570 whereupon the roles assigned to the user arestored (step 580). Processing then returns at 595.

FIG. 6 is a flowchart showing steps taken by the administrator to set upa workstation. Processing commences at 600 whereupon and identifier,such as a MAC address, if entered for workstation (step 610). A MACaddress is a Media Access Control address which is a hardware addressthat uniquely identifies each node of a computer network. A host, orserver, is assigned to the workstation (step 620). An IP address iseither assigned or retrieved for the workstation (step 630). Aworkstation description is also entered for the workstation (step 640).A workstation description may include a description of the workstation'scapabilities, such as whether the workstation includes a bank tellerdrawer.

The first role for the workstation is selected (step 650) from a list ofroles that was created by the administrator and stored in data store660. For example, in a banking environment, roles may include a teller,a loan officer, and a branch manager. One workstation may be capable ofperforming all three roles, while another is only capable of performingone or two of the roles. Furthermore, confidential or sensitivefunctions may be restricted to a particular workstation even thoughother workstations may be physically capable of performing suchfunctions. A determination is made as to whether there are more roles toassign to the workstation (decision 670). If there are more roles toassign to the workstation, decision 670 branches to “yes” branch 675whereupon the next role for the workstation is selected (step 680). Thislooping continues until there are no more roles to assign to theworkstation, at which point decision 670 branches to “no” branch 685.The assigned roles and workstation data are stored (step 690) in anonvolatile storage area. Processing then returns at 695.

FIG. 7 is a flowchart showing steps taken by the administrator to set upapplication extensions. Application extensions are desktop componentsthat provide access to application programs, such as client-based legacyapplications. Processing commences at 700 whereupon an extensionidentifier is assigned to the particular application extension (step705). An application description is entered describing the correspondingapplication (step 710). A client class for the application extension isalso entered (step 715).

A determination is made as to whether the extension is provided by thesystem or is provided by the user (decision 720). If the extension isprovided by the user, decision 720 branches to user branch 725 whereuponthe Java archive (JAR) filenames corresponding to the extension areentered (step 730). On the other hand, if the extension is systemsupplied, decision 720 branches to system branch 735 bypassing step 730.

A determination is made as to whether an administrator object orientedclass is needed (decision 740). If an administrator class is needed,decision 740 branches to “yes” branch 745 whereupon the administratorclass name is entered (step 750). On the other hand, if an administratorclass is not needed decision 740 branches to “no” branch 755 bypassingstep 750.

The application extension is created using the supplied information(step 760). A determination is made as to whether there are any defaultproperties for the application extension (decision 770). If there aredefault properties, decision 770 branches to “yes” branch 775 whereuponthe default properties are entered for the application extension (step780). On the other hand if there are no default properties for theapplication extension, decision 770 branches to “no” branch 785bypassing step 780.

The application extension, along with any default properties, is stored(step 790) in a nonvolatile storage area. Processing then returns at795.

FIG. 8 is a flowchart showing administrator steps taken to set upapplication references. Processing commences at 800 whereupon the typeof reference (i.e., the extension type) corresponding to the applicationreference is selected (step 810). A unique application referenceidentifier is assigned to the application reference (step 820). Anapplication description is also provided for the application reference(step 830). Icon attributes, such as the icon titles and icon filenames,are also provided (step 840). Properties that are specific to the typeof the application extension are also entered (step 850). Theapplication reference is then stored in a nonvolatile storage area (step860) and processing returns at 895.

FIG. 9 is a flowchart showing steps taken by an administrator to createself-contained desktops. Processing commences at 900 whereupon a uniquedesktop identifier is assigned to the self-contained desktop (step 905).A desktop title and/or description is entered for the desktop (step910). The screen and icon appearance is entered for the desktop (step915). The administrator then selects images, such as icons, backgrounds,etc., to appear on the desktop (step 920). These images are selectedfrom desktop component library 925. The desktop component library 925includes backgrounds and other images 930, icons 935, applicationreferences 945, and resources 955.

Application references that will be available from the desktop areselected (step 940) from application references 945 included in desktopcomponent library 925. In a banking environment, a teller's desktop caninclude application references to look up customer bank balances andoperate the teller's cash drawer, while a loan officer's desktop caninclude application references that provide access to the bank's loanapproval software application. National language data, such as text andresources, are provided for each supported locale (step 950). Theseresources are selected from resources 955 that are included in desktopcomponent library 925.

The desktop configuration is stored detailing the files and resourcesincluded the desktop (step 960). A client configuration file describingthe desktop is created and the desktop data is packaged (step 970)resulting in self-contained desktop 975. The resulting self-containeddesktop is published to client-accessible servers (step 980) bytransmitting the desktops to servers 990. Processing then returns at995.

FIG. 10 is a flowchart showing steps taken by a server to deliverself-contained desktops to a client. Processing commences at 1000whereupon the server receives a user login and workstation identifier(step 1005). The user login includes a user identifier and a userpassword used to authenticate the user. Roles that have been assigned tothe user are retrieved (step 1010) from user directory data store 1015.Roles that have been assigned to the workstation are retrieved (step1020) from topology directory 1025.

A determination is made as to whether any roles assigned to the usermatch any roles assigned to the workstation (decision 1030). If thereare no roles in common, decision 1030 branches to “no” branch 1035whereupon an error is returned to the client (step 1038) and processingreturns at 1095. On the other hand, if there are one or more roles incommon, decision 1030 branches to “yes” branch 1040 whereupon the firstdesktop for the selected role is retrieved from desktop/role map 1050and the corresponding self-contained desktop is retrieved from datastore 1055. A determination is made as to whether there any more rolesin common between the user and the workstation (decision 1060). If thereare more roles in common, decision 1060 branches to “yes” branch 1070whereupon the next common role is selected (step 1080) and processingloops back to retrieve the corresponding self-contained desktop. Thislooping continues until there are no more roles in common between theuser and workstation, at which point decision 1060 branches to “no”branch 1065 whereupon the retrieved desktop identifiers (i.e. thoseidentifiers in common for both the user and the workstation) are sent tothe client (step 1090). Processing then returns at 1095.

FIG. 11 is a screen layout of a screen used by an administrator to setup a new site. The administrator uses screen layout 1100 to define a newsite. The administrator enters a unique site identifier in text box1150. If the new site is a child of a site that has already beencreated, the parent site is selected from list box 1105. List box 1105includes a list of previously defined site identifiers. Frame 1110includes policy information that is used for the site. Policyinformation includes a policy name 1115, a policy value 1120, andinheritance data 1125. Inheritance data 1125 includes inheritance value1130 and inheritance ancestor 1135. In the example shown, the policyname is “newbDC” and the value of the policy is inherited from theparent site. The inheritance value is “allow” and the inheritanceancestor is the “root” or uppermost site in the site hierarchy.

Desktop frame 1140 includes information about the roles and desktopsavailable at the site. Desktop frame 1140 includes role data 1155,desktop data 1160, and inheritance data 1170. The inheritance dataincludes the name of the desktop that is inherited 1175 and the name ofthe ancestor 1180 from which the desktop is inherited. In the exampleshown, the roles included at the site include the administrator, abranch manager, a guest, a loan officer, and a teller. Each of thedesktops is inherited from the parent site as shown by the “[Inherited]”value for the desktop field. The administrator, branch manager, and loanofficer desktops are inherited from “BranchA” site, while the guest andteller desktops are inherited from the “root” site. In this manner,self-contained desktops can be selected from a variety of parent sitesor can be specifically configured for the child site.

When the new site data has been entered, the administrator selects“Create Site” command button 1190 to create the new site. If theadministrator makes mistakes and wishes to reset the values, theadministrator can select “Reset Values” command button 1195.

FIG. 12 is a screen layout of a screen used by an administrator tomanage desktops and machines for a given site. The administrator usesscreen layout 1200 to manage desktops for a given site as well as to addand manage workstations that correspond to the site. The top half ofscreen layout 1200 is similar to the new site layout shown in FIG. 11.List box 1205 is used to select the parent site to assign to the site.The parent site can be changed to accommodate changes within theorganization. Policy frame 1210 include the name of the policy 1212, thepolicy value 1214, and inheritance data 1216. The inheritance dataincludes inheritance value 1218 and ancestor value 1220. In the exampleshown, the policy name is “newbDC” which is inherited from the “root”ancestor.

Desktop frame 1225 includes role data 1230, desktop data 1235, anddesktop inheritance data 1240. In the banking example that is shown inFIG. 12, the roles included for the site consist of an administrator, abranch manager, the guest, a loan officer, and a teller. The desktop tobe used by the administrator, branch manager, guest, loan officer, andteller. Each of these roles is shown in desktop data 1235. Some of thevalues are inherited from a parent site while others are specified to bea particular self-contained desktop. Desktop inheritance data includesdesktop inheritance 1242 and ancestor data 1244. In the example shown,the administrator, branch manager, and loan officer each inherit desktopdata from “BranchA”, while the guest and teller each inherit desktopdata from the “root” parent.

If the administrator changes the site data and wishes to store thechanged site information, the administrator selects “Submit Changes”command button 1245. If the administrator wishes to reset the sitevalues, the administrator selects “Reset Values” command button 1250. Ifthe administrator wishes to delete the site, the administrator selects“Delete Site” command button 1255.

When the administrator is ready to publish the site to the servers, theadministrator selects “Publish” command button 1260. If theadministrator wishes to publish the site along with any sites that arechildren of the site, the administrator selects “Publish with Children”command button 1265.

Child sites frame 1270 includes data regarding any sites that arechildren of the site. Child site data includes site name 1272 and sitepolicies 1278. To create a new child site, the administrator can select“<New Site>” hyperlink 1275 which will allow the administrator toidentify a new child site.

Machines frame 1280 includes data about workstations included at thesite. Workstation data includes the workstation identifier 1282, thehost name for the workstation 1284, the workstation type 1286, the rolesprovided by the workstation 1288, the workstation's IP address 1290, andthe workstation description 1292. To add a new machine (workstation) tothe site the administrator selects “<New machine>” hyperlink 1295.

FIG. 13 is a screen layout of a screen used by an administrator to setup a new user. Screen layout 1300 includes text box 1305 for enteringthe new user's unique identifier. The user's full name is entered intext box 1310. In addition, the description of the user can be enteredin text box 1315. For example, a user ID may be set up as a genericidentifier such as a guest or teller that can be used by someone withouthaving to establish a new user identifier for such infrequent orpart-time users. The user identifiers used for such generic purposes canbe further described using description text box field 1315.

A new initial password is entered for the user in text box 1320. Thisnew initial password is confirmed by the administrator by reentering thepassword in text box 1325. A default locale is selected by theadministrator for the user using list box 1330. In the example shown,the locale has been selected to be a U.S. locale for a user speakingU.S. English. However, if the user's primary language was Spanish orsome other language, the appropriate locale is selected from the listprovided in list box 1330.

Frame 1332 is used by the administrator to select the roles thatcorrespond to the user. Default role 1335 includes a number of radiobuttons corresponding to each of the available roles. Radio buttons areused so that the administrator only selects one default role for theuser. Select column 1340 includes a number of checkboxes correspondingto each of the available roles. The administrator selects each of thecheckboxes corresponding to each role that is performed by the user.Name column 1345 includes the name of each of the available roles. Inthe example shown, the available roles include an administrator, branchmanager, the guest, a loan officer, and a teller. The administrator canselect one or more of these roles by selecting the correspondingcheckboxes in column 1340. In addition, the administrator can establisha new role by selecting “<New Role>” hyperlink 1350.

When the administrator is finished entering the user data and assigningroles to the user, the administrator selects “Create User” command box1355 to create and store the user data and assigned roles. If theadministrator makes mistakes and wishes to reset the values, “ResetValues” command button 1360 is selected.

FIG. 14 is a screen layout of a screen used by an administrator to setup an application that is available as a component within one or moreself-contained desktops. Screen layout 1400 is used to define a newapplication that can be included in self-contained desktops. Applicationidentifier text box 1405 is used by the administrator to enter a uniqueapplication identifier that corresponds to the application that is beingdefined. In the example shown in FIG. 14, the type of application beingdefined is a “native” application, in other words an application whereinat least some of the application's executables reside on the clientworkstation.

A description of the application that is being defined is entered indescription text box 1410. Icon attributes frame 1415 is used to definethe attributes corresponding to the icon that will appear on the desktopand be used by the user to select the application. Icon attributesinclude a title that is entered in text box 1420 and an icon filenamethat is entered in text box 1425.

Platform properties frame 1430 includes data for each of the supportedoperating system platforms from which the application can be invoked.Win32 frame 1435 includes data which is used to invoke and execute theapplication from a Microsoft Windows operating system platform. TheWin32 data includes a path and filename identifying the executable formof the application in the Win32 environment. The path and filename isentered in text box 1440. Any parameters that are needed for theapplication are supplied in parameters text box 1445. A workingdirectory that corresponds to the application, if needed, is entered intext box 1455.

Platform properties frame 1430 also includes data for the OS/2 operatingsystem platform, the fields for which are located in frame 1460. TheOS/2 fields correspond to the Win32 fields described above. Theseinclude path and filename text box 1465, parameters text box 1470, andworking directory text box 1475. Likewise, a Linux set of fields isprovided in frame 1480 which includes path and filename text box 1482,parameters text box 1484, and working directory text box 1486.

When the application information has been entered by the administrator,the administrator can create the application by selecting “CreateApplication” command button 1490. If the administrator makes mistakes, anew application values can be reset by selecting “Reset Values” commandbutton 1495.

FIG. 15 is a screen layout of a screen used by an administrator to setup a self-contained desktop. Screen layout 1500 includes various fieldsused to define the appearance and functionality of a self-containeddesktop. The desktop identifier, which was previously defined, isdisplayed on the screen. In the example shown, the desktop identifier is“bda-administrator.” The title for the self-contained desktop is enteredby the administrator in text box 1505. In the example shown, the titleis “Administrator.” A description for the self-contained desktop isentered in text box 1510. In the example shown, the description enteredis “Desktop for BDA Admins.”

A launch mode for the self-contained desktop is selected by theadministrator using list box 1515. The launch mode indicates the numberof mouse clicks needed to activate a component from the desktop. In theexample shown, the launch mode selected is “2” (i.e., a double-click).Icon attributes are entered in frame 1520. Maximum allowable anddisplayable icon title lengths are entered by the administrator in theappropriate text boxes.

Background appearance information is entered by the administrator inframe 1525. The color, image file, and image display mode are providedby the administrator for the background of the self-contained desktop.For example, desktop background data can include the name and logo ofthe organization. Icon appearance information is entered by theadministrator in frame 1530. Icon appearance data includes the textcolor of the icon, the font that is used with the icon, the font sizethat is used with the icon, the font style that is used to the icon, theicon flow, the origination point of the icon flow, and the text positionfor the icon text.

When the administrator has completed setting up the self-containeddesktop, the administrator selects “Submit Changes” command button 1540to save the desktop settings. If the administrator makes mistakes orwishes to reset the values, the administrator selects “Reset Values”command button 1545. If the administrator wishes to delete theself-contained desktop definition, the administrator selects “DeleteDesktop” command button 1550.

Hyperlink 1560 is used to add, modify, or delete references that areavailable from the self-contained desktop. The references that areavailable include applications 1570, folders 1580, and toolbars 1590. Inthe example shown, the applications that had been included consist of“acroread,” “calculator,” and “browser.” The folders that are includedconsist of an applications folder, and two administrator folders. Onetoolbar, the Admin Toolbar, is also included.

FIG. 16 is a screen layout of a screen used by an administrator tomanage workstations. Screen layout 1600 is used by the administrator tomanage the workstations, or computer systems, used throughout thenetwork. Data maintained for each of the workstations includes theworkstation identifier which is listed in column 1610, the site to whichthe workstation belongs which is listed in column 1620, the host (orserver) assigned to the workstation which is listed in column 1630, thetypes of functions performed by the workstation which are listed incolumn 1640, the roles that the workstation is allowed to perform whichare listed in column 1650, the workstation's IP address which is listedin column 1660, and a description for the workstation which is listed incolumn 1670.

The identifiers shown in column 1610 are unique for each workstation. Inthe example shown in FIG. 16, the identifiers are the MAC addresses thatcorrespond to the workstations. The sites shown in FIG. 16 are eitherthe “root” site, branch “A”, or branch “B.” These sites may representphysical or logical regions within the organization. The host name isthe name of the server used by the workstation. The types of functionsperformed by the workstation include administration functions, serverfunctions, and client functions. Types ending with “A” are used foradministration functions, types ending with “S” are used for serverfunctions, and types ending with “C” are used for client functions. Ascan be seen in FIG. 16, some workstations perform multiple types offunctions. For example, the first workstation listed serves bothadministrator and server functions. Roles indicate the functions allowedto be performed on the workstation. Roles typically relate to clientfunctions, so therefore workstations that do not have a client type donot have roles assigned. Workstations that have assigned roles oftenhave multiple roles. For example, the third workstation listed has fourroles that are allowed to be performed on the workstation (teller,loan-officer, branch manager, and guest). However, the fourth and fifthworkstation shown only have one role that is allowed to be performed oneach workstation. The IP address is the network address that is assignedto the workstation. In some environments the IP address is a staticaddress, while in other environments the IP address is dynamicallyassigned. The description of each workstation is optional, yet helps theadministrator better identify particular workstations and the roles suchworkstations play.

FIG. 17 is a flowchart showing steps taken to distribute self-containeddesktops to servers. Administrator desktop distribution processingcommences at 1700 whereupon the first desktop for distribution isselected (step 1705). A request is created with the desktop name and aunique signature, such as a CRC value (step 1710). The created desktoprequest is sent to one or more servers (step 1715). A determination ismade as to whether there are more desktops to distribute (decision1720). If there are more desktops to distribute, decision 1720 branchesto “yes” branch 1722 whereupon processing selects the next desktop fordistribution (step 1725) and loops back to create the request and sendthe request to the servers. This looping continues until there are nomore desktops to distribute, at which point decision 1720 branches to“no” branch 1728.

Server responses resulting from the previously sent desktop request arereceived by the administrator (step 1730). A determination is made basedupon the response as to whether the desktop already exists at the server(decision 1735). If the desktop does not yet exist at the server,decision 1735 branches to “no” branch 1738 whereupon the identifieddesktop is sent to the server in a data stream (step 1740). On the otherhand, if the desktop already exists at the server decision 1735 branchesto “yes” branch 1742 bypassing step 1740.

A determination is made as to whether there are more responses toreceive from servers regarding the desktop request (decision 1745). Ifthere are more responses, decision 1745 branches to “yes” branch 1746 toloop back and process the responses. This looping continues until thereare no more responses to process, at which time decision 1745 branchesto “no” branch 1748 and administrator desktop distribution processingends at 1750.

Server desktop collection processing commences at 1755 whereupon theserver receives the desktop distribution request sent by theadministrator (step 1760). The unique identifier for the desktopincluded in the administrator's request is compared with desktop data1768 that is currently on hand at the server (step 1765). Adetermination is made based upon the comparison as to whether thedesktop is needed by the server (decision 1770). If the desktop is notneeded (i.e. the desktop already exists at the server) decision 1770branches to “no” branch 1772 whereupon a message is sent to theadministrator indicating that the server already has the desktop (step1775) and server processing ends at 1795.

On the other hand, if the server does not yet have the desktop decision1770 branches to “yes” branch 1778 whereupon the server request thedesktop (step 1780). The server receives the desktop data stream inresponse to the request (step 1785). The server then creates aself-contained desktop file from the received data stream and stores thedesktop file in desktop data storage area 1768 (step 1790). Serverdesktop collection processing then ends at 1798.

FIG. 18 is a flowchart showing steps taken to distribute self-containeddesktops from a server to a client. Client desktop reception commencesat 1800 whereupon the client sends a desktop list request to a server(step 1805). The desktop list request includes the client's machine(workstation) identifier and the client's user identifier.

Server desktop distribution processing commences at 1840 whereupon theserver receives the desktop list request from the client (step 1845).The server looks up the roles that have been assigned to the user (step1850) by searching user roles data store 1852. The server also looks upthe roles that have been assigned to the workstation being used by theuser (step 1855) by searching machine roles data store 1858.

The server retrieves desktop information based upon the intersection, oroverlap, between the user roles and the machine roles (step 1860) andlocates the desktops that correspond to the overlapping roles in desktopdata store 1862. The desktop information that is retrieved includes adesktop identifier and a desktop signature, such as a CRC, that is usedto uniquely identify the desktop. A user may have a default role and adefault desktop that corresponds that role. If the user has a defaultrole, the server determines the default role (step 1865).

The server creates a response string (step 1870) of valid roles, desktopsignatures, a default desktop identifier (if applicable), and a defaultrole (if applicable). The server then returns the response string to theclient (step 1875).

The client receives the desktop list that includes the roles that havebeen assigned to both the user and the workstation along with anydefault role and default desktop information from the server (step1810). The client compares the desktops included in the desktop listwith desktops that have already been cached on the client workstation(step 1815). This is done so that the client only needs to request thosedesktops that have not previously been transmitted to the clientworkstation and cached in the workstations volatile or nonvolatilestorage areas.

The client determines whether additional components, or desktops, areneeded from the server by identifying such desktops or components thathave not yet been cached on the client workstation (decision 1820). Ifthe client determines that no additional desktop components are needed,decision 1820 branches to “no” branch 1832 (bypassing the steps used torequest and retrieve additional desktop information) and clientprocessing ends at 1835.

On the other hand, if the client needs additional components ordesktops, decision 1820 branches to “yes” branch 1822 whereupon theneeded desktops are requested from the server (step 1825). This requestis received by the server at server step 1885. The server responds byretrieving the request desktop information from desktop data store 1862and returning it to the client workstation (step 1890). The serverdesktop distribution processing then ends at 1895.

Returning to client processing, the client receives and caches therequested desktop information at step 1830 and client desktop receptionprocessing ends at 1835.

FIG. 19 is a flowchart showing steps taken to create custom applicationextensions. Custom application extensions allow a third party to extenda preexisting object oriented class to modify the behavior or attributesof a server class object to better serve the needs of a particularorganization. Custom application extension creation processing commencesat 1900 whereupon the client object oriented class is provided thatimplements a particular component interface (step 1910). A determinationis made as to whether to extend the server abstract class (decision1920). If the abstract class is not being extended, decision 1920branches to “no” branch 1925 whereupon the default server component isused for the component interface (step 1930). On the other hand, if theabstract class is being extended, decision 1920 branches to “yes” branch1935 whereupon the server class that extends the server componentabstract class is provided (step 1940).

A determination is made as to whether additional resources are neededfor the custom application extensions (decision 1950). If additionalresources are needed, decision 1950 branches to “yes” branch 1955whereupon the additional resources used by the application extension areprovided (step 1960). The additional resources may include images,property files, and other class files used by the application extension.On the other hand, if additional resources are not needed decision 1950branches to “no” branch 1965 bypassing step 1960.

The client classes, server classes, and any additional resources arepackaged in Java archive (JAR) files (step 1970). The packaged customextensions are stored in custom extensions library 1980. The creation ofcustom application extension process ends at 1995.

FIG. 20 is a flowchart showing an application extension lifecycle. Theapplication extension lifecycle begins at step 2000. During the firstphase of the application extension lifecycle, the application extensionuses a no-arg constructor (step 2025). The no-arg constructor is used tocreate the application extension component by loading its Javaimplementation class and invoking a no-arg constructor. At this point,the application extension component has no reference to the clientdesktop and cannot interact with the desktop environment. During thisphase, instance variables and default settings are initialized.

During the next phase of the application extension lifecycle, theapplication extension initializes (step 2050). During the initializationphase, the initialized method corresponding to the application extensionis defined in the component interface. References to componentconfiguration items, initial locale information, and desktop referencesare also provided. Desktop references are preferably saved as instancevariables during this phase.

During the final phase of the application extension lifecycle, the startmethod corresponding to the application extension is invoked (step2075). The start method is called by the desktop. For example the startmethod may be called when the icon corresponding to the applicationextension is selected by a user. During this phase, the applicationextension may use desktop references as well as references to otherdesktop components. In addition the application extension may at thistime start threads and perform I/O operations.

FIG. 21A is a block diagram showing components and resources beingdistributed from an administrator to multiple clients. Administrator2100 publishes components and resource libraries 2105 that had beenpackaged into various desktop packages 2110 by transmitting thesepackages to various servers.

In the example shown in FIG. 21A, there are three servers that receivedesktop packages from the administrator. The servers include server2120, server 2140, and server 2160. Each of the servers includes anonvolatile storage area for storing desktop packages receive from theadministrator. Server 2120 uses nonvolatile storage area 2125 forstoring desktop packages, server 2140 uses nonvolatile storage area2145, and server 2160 uses nonvolatile storage area 2165. The desktoppackages are distributed from the administrator to the servers in theprocess described in FIG. 17. The servers are used to provide desktoppackages to various clients.

In the example shown in FIG. 21A, there are two clients that receivedesktop packages from each of the servers. Clients 2130 and 2135 receivedesktops from server 2120, clients 2150 and 2155 receive desktops fromserver 2140, and clients 2170 and 2175 receive desktops from server2160. The desktops are distributed from the servers to clients using theprocess described in FIG. 18. In this manner, components and resourcesused in the various self-contained desktops are distributed from anadministrator throughout the system to servers and eventually toclients.

FIG. 21B is a block diagram showing components and resources beingrecovered by an administrator from servers following a data loss by theadministrator. When a disaster event, such as a computer crash, fire, orflood occurs, the administrator may be left without the components andresources used to create the various self-contained desktops. In orderto recover these files, administrator 2100 requests desktop packages,including the components that comprise the desktop packages, from thevarious servers. Using the topography described in FIG. 21A, theadministrator requests packages from servers 2120, 2140, and 2160. Theservers retrieve self-contained desktop packages that include desktopcomponents from storage areas 2125, 2145, and 2165 respectively. Thedesktop information is transmitted from the various servers back to theadministrator. The administrator stores the received self-containeddesktop packages in restored package library 2180. The components andresources that are included in the self-contained desktops are extractedfrom the desktop files and stored in restored components and resourcelibraries 2190. In this manner, the administrator is able to recover andrestore the components and resources that had previously been publishedto the various servers. This recovery is performed without having tohave the administrator make separate backup copies of the components andresources. Because components and resources include unique identifiers,multiple versions, or levels, of components and resources are also ableto be recovered. A flowchart showing the steps taken by theadministrator to recover desktop data is shown in FIG. 22.

FIG. 22 is a flowchart showing steps taken by an administrator indistributing self-contained desktops and subsequently recoveringself-contained desktops following a disaster event. Administratorprocessing commences at 2200 whereupon the administrator createscomponents and resources (step 2205) that will be used in self-containeddesktops. These components and resources are stored in a library that isstored in nonvolatile storage area 2210.

The components and resources are packaged (step 2215) into variousself-contained desktops for use by various users based upon the users'roles. The self-contained desktops are stored in self-contained desktoplibrary 2225. The self-contained desktops are distributed (step 2220) tovarious servers. Administrator distribution processing ends at 2230.Further detail regarding the distribution of self-contained desktops canbe found in FIG. 17.

Server reception of self-contained desktops commences at 2235 whereuponthe server receives the self-contained desktop packages (step 2240) andstores the received packages in nonvolatile storage area 2245. Theserver then distributes self-contained desktops to clients has needed(step 2250). Further detail regarding the distribution of self-containeddesktops to clients can be found in FIG. 18.

At some point, a disaster event occurs destroying packages, resources,and components from the computer system and storage devices use by theadministrator (step 2255). The self-contained desktop information isthen recovered by the administrator using the recovery processcommencing at step 2260. The administrator identifies unique packagesthat have been destroyed and are no longer stored on the administrator'scomputer system (step 2265). The identified packages are requested fromthe various servers (step 2270).

The servers receive desktop package requests from the administrator(step 2275). The requested desktop packages are retrieve from theserver's nonvolatile storage area 2245 and transmitted to theadministrator's computer system (step 2280) and server recoveryprocessing ends at 2295.

The administrator computer systems receives the self-contained desktoppackages sent by the servers and stores the received desktop packages inpackage library 2225 (step 2285). The self-contained desktop packagesare unpacked and the components and resources that are included inself-contained desktop packages are used to repopulate components andresource libraries 2210 (step 2290). At this point, all packages,components, and resources that were previously distributed by theadministrator have been recovered and stored in the appropriatelibraries. Administrator recovery processing then ends at 2298.

FIG. 23 is a flowchart showing steps taken by a client to receive anddisplay desktops based upon the client's role (or roles) in theorganization. Processing commences at 2300 whereupon the client machinereceives the first desktop from server (step 2305). The received desktopis stored on client's local storage 2315, either in a volatile or anonvolatile storage area (step 2310).

A determination is made as to whether the received desktop is thedefault desktop for the client (decision 2320). If the receive desktopis the default desktop, decision 2320 branches to “yes” branch 2325whereupon the received desktop is displayed on the client's displaydevice (step 2330). On the other hand, if the received desktop is notthe default desktop, decision 2320 branches to “no” branch 2335bypassing step 2330.

A determination is made as to whether there are more desktops for theclient machine to receive from the server (decision 2340). If there aremore desktops to receive, decision 2340 branches to “yes” branch 2345whereupon processing loops back to receive the next desktop (step 2350)and determine whether the next desktop is the default desktop. Thislooping continues until all needed desktops have been received from theserver, at which point decision 2340 branches to “no” branch 2355.

A determination is made as to whether more than one desktop isaccessible by the client (decision 2380). If more than one desktop isaccessible, decision 2380 branches to “yes” branch 2385 whereupon theavailable desktop descriptions are inserted as items within a pop-upselection window that is accessible by the client (step 2390). Forexample, the user could “right” click in the desktop area usingappointing device, such as a mouse, which would cause the pop-up menu tobe displayed. The user could then select the desired desktop from thelist provided in the pop-up menu (see FIG. 27 for an example desktopscreen and pop-up menu). For example, if a branch manager also has anassigned role of a loan officer, the branch manager can select the loanofficer desktop from the pop-up menu. After selecting the loan officerdesktop, the desktop components used for loan officer functions would bedisplayed and be accessible from the desktop area. On the other hand, ifthere are no more than one desktop accessible by the client, decision2380 branches to “no” branch 2392 bypassing step 2390. Display desktopprocessing then ends at 2395.

FIG. 24 is a flowchart showing steps taken by a server to providedesktop information to a client based on the user's role and theworkstation's role. Processing commences at 2400 whereupon the serverreceives a desktop request (step 2405) from client 2410. The requestincludes the client's user ID, password, and the client workstation'sMAC address.

The server looks up the client's MAC address (step 2415) fromworkstation table 2420 that includes the roles that are allowed to beperformed on various workstations. In the example shown, the workstationwith a MAC address of “123” is allowed to perform both teller and loanofficer functions, while the workstation with a MAC address of “456” isonly allowed to perform branch manager functions.

A determination is made as to whether the client's MAC address was foundin the workstation table (decision 2425). If the MAC address was notfound, decision 2425 branches to “no” branch 2428 whereupon adetermination is made as to whether client workstation registration isrequired by the system (decision 2430). If workstation registration isrequired, decision 2430 branches to “yes” branch 2430 whereupon an erroris returned to the client (step 2435) indicating that the client'sworkstation is not registered and server processing ends at 2440. On theother hand, if workstation registration is not required decision 2430branches to “no” branch 2442 and processing continues. Returning todecision 2425, if the client's MAC address was found in the workstationtable, decision 2425 branches to “yes” branch 2445 and processingcontinues.

The first desktop that has been assigned to the user's identifier (userID) is retrieved (step 2450) from user desktop table 2455. In theexample shown, the user ID “Able” has been assigned to the “teller”role, while the user ID “Jones” has been assigned to the “teller,” “loanofficer,” and “branch manager” roles. A determination is made as towhether the retrieved desktop assigned to the user is allowed to be usedon the workstation that is being used by the user (decision 2460). Ifthe desktop is allowed to be used to the workstation, decision 2460branches to “yes” branch 2465 whereupon the desktop is sent to theclient (step 2470). On the other hand, if the retrieved desktop is notallowed to be used on the workstation, decision 2460 branches to “no”branch 2472 bypassing step 2470.

A determination is made as to whether there are more roles, or desktops,that have been assigned to the user (decision 2475). If there are moreroles that have been assigned to the user, decision 2475 branches to“yes” branch 2480 whereupon the next desktop assigned to the user isselected (step 2485) and processing loops back to determine whether thenext desktop should be set to client. This looping continues until alldesktops assigned to the user have been processed, at which pointdecision 2475 branches to “no” branch 2490 and server processing ends at2495.

FIG. 25 is a block diagram showing processing performed by a server andinteraction between the server, clients, and administrator. Server 2500performs role identification function 2570 by receiving role assignmentsfrom administrator 2575. Role assignments included roles that have beenassigned to the user as well as roles that have been assigned toworkstations located throughout the network. Workstation roles arestored in workstation role data store 2560. The user roles are stored inuser role data store 2555.

Server 2500 also performs desktop collection processing 2580 byreceiving desktop information from administrator 2575. The desktopinformation is stored in desktop definition data store 2590. The desktopinformation includes self-contained desktops that, in turn, includeddesktop components and resources for use by client 2525.

Server 2500 receives authentication information from client 2525, suchas a user ID and password, which is used to authenticate the client.Server 2500 performs authentication processing 2510 by checking theclient's authentication information with authentication data that islocated in authentication data store 2520. Once the client has beenauthenticated, the client receives access to client's data storage area2540 which is stored on server 2500. The server provides access to theclient's data storage by performing home directory access process 2530.In this manner, a user can access his or her data regardless of whichworkstation he or she is using.

Server 2500 performs desktop distribution process 2550 to determinewhich self-contained desktops to send to client 2525. Desktopdistribution process 2550 is performed by comparing user roles stored inuser role data store 2555 with workstation roles stored in workstationrole data store 2560. Desktops, or roles, that are assigned to both theuser and the workstation are distributed to the client. Server 2500retrieves the desktop information from desktop data store 2590 andtransmits the desktop information to client 2525.

FIG. 26 is a flowchart showing steps taken by a client in initializingand displaying self-contained desktops. Client 2600 performsauthentication request, home directory request, and password updates bysending the corresponding information to the server. Client 2600 uses anunderlying operating system platform 2610 to perform native operations.JSLLIB 2680 is a native library that includes native commands andprograms used to perform native operations.

Shell 2605 is a Java-based application that is adapted to run on any ofthe operating system platforms used in the system (e.g., Windows XP™,OS/2™, or Linux™). The shell makes a determination as to whether theclient login is performed remotely through a server or locally (decision2620). If the login is performed remotely, decision 2620 branches to“yes” branch 2622 whereupon the client receives desktops from the server(step 2625). In one embodiment, the desktops are received by firstreceiving a list of desktops and then retrieving individual desktopsfrom the list.

The list, or map, of desktops is cached to local storage located on theclient machine (step 2630). The received desktops are also cached tolocal storage (step 2635). Returning to decision 2620, if the desktopsare not retrieved remotely, decision 2620 branches to “no” branch 2638bypassing steps 2625, 2630, and 2635.

The desktops that have been assigned to both the user and theworkstation are retrieved from local storage (step 2640). Local storageis used to store user desktop map 2660 and desktops 2670. Desktops areself-contained packages that include desktop components and resourcesneeded to display and execute the desktop. The retrieved desktopinformation is used to create desktop objects (step 2645). Desktop classloader 2650 is used to create the desktop objects. Resources, such asnational language translations, are loaded from the desktop information(step 2655). Desktop class loader 2650 is also used to load the neededresources.

At this point, the desktops assigned to the user in workstation havebeen retrieved and made available to the user within shell 2605. Desktopobjects and resources have been extracted from the self-containeddesktops and have been made available to the user through shell 2605.

FIG. 27 is a screen layout of a sample desktop displayed on a clientworkstation along with a pop-up menu of other self-contained desktopsavailable to the client. Desktop screen layout 2700 includes a number ofobjects 2750. Objects 2750 include desktop components that areaccessible from the desktop. Each desktop component corresponds to agraphical image, such as an icon, which is selectable by the user usinga pointing device such as a mouse.

Pop-up menu 2710 includes two items allowing the user to either changethe desktop or display the shell version. Selecting the “Change Desktop”item causes the display of desktop selection menu 2720. The user selectsthe desktop that is desired by placing a check mark in the box besidethe desired desktop. In the example shown, the “administrator” desktopis being displayed on the client display as evidenced by the check markshown in desktop selection menu 2720. If the user wishes to change thedesktop, for example to the branch manager desktop, the user simply usesa pointing device, such as a mouse, and places a check mark in the boxnext to the “branch manager” menu item.

Components 2750 may change depending upon the desktop that has beenselected. For example, the “Branch Desktop Administrator” desktopcomponent is displayed because the “Administrator” desktop has beenselected. However, if another desktop, such as the “Teller” desktop, isselected, the “Branch Desktop Administrator” will no longer appear andwill not be accessible from the display. In this manner, components fora selected role are displayed and accessible, while components used by adifferent role are not displayed and are not accessible. Moreover,components that are used by multiple roles are each available from thevarious desktops that correspond to the roles.

FIG. 28A is a hierarchy chart of directories used by the client shell indisplaying and managing desktops. Shell home directory 2800 includes anumber of subdirectories used by the client for performing desktopfunctions. In one embodiment, the shell home directory and itssubdirectories are stored on a server accessible by the client. Inanother embodiment, the shell home directory and its subdirectories arestored on a nonvolatile storage device local to the client machine.Native library 2805 is a subdirectory used to store programs used tointerface with the client's operating system platform. In oneembodiment, native library information is stored in Java archive (JAR)files. Properties subdirectory 2810 is a subdirectory used to storeproperties that are used by the shell program. These properties caninclude display attributes and other configuration items used by theshell program.

Desktop subdirectory 2815 is the directory in which self-containeddesktop files are stored. In one embodiment, self-contained desktopfiles are packaged into Java archive (JAR) files. In this manner, allcomponents and resources used by particular desktop are packaged andincluded in a self-contained desktop JAR file. Log subdirectory 2820 isused to store client-based logs that detail the actions taken by theclient. “Conf” subdirectory 2825 is used to store initializationinformation used by the shell application. “Bin” subdirectory 2830 isused to store executables, such as program files, that are used tolaunch the shell application.

FIG. 28B is a hierarchy chart of sections included with the shellconfiguration file. The shell configuration file includes number ofsections. Each of these sections includes information about a particularaspect of the shell. In one embodiment, the shell configuration file isan XML file that includes a number of sections. The sections includelocales section 2840 that includes information about the locale, such asnational language translations, used by the shell application. Componentsection 2845 includes information about the components that are includedwith the self-contained desktop. Components include applications andother programs that are accessible from the desktop when the userselects an appropriate icon or other command. Folders section 2850includes information about the various folders that are accessible fromthe desktop. Toolbars section 2855 includes information about thevarious toolbars that are displayed and accessible from the desktop.Desktop section 2860 includes information about the desktop, such asappearance data and policy information.

FIG. 28C is a hierarchy chart of objects included in the self-containeddesktop file. In one embodiment, the self-contained desktop is a Javaarchive (JAR) file. Self-contained desktop file 2865 includes number ofcomponents. The components include manifest 2870 which details theobjects included in the self-contained desktop file. The components alsoinclude a Shell Document Type Definition (DTD) object 2875. The ShellDTD object states what kinds of attributes are used to describe contentin the Shell XML document, where each tag is allowed, and which tags canappear within other tags. Classes objects 2880 include the Java classesthat are used by the desktop. Resources 2885 include resourceinformation, such as national language translation information, that isused by the desktop. JAR objects 2890 include additional objects neededby the desktop that are packaged into further JAR files. XML object 2895includes the XML document that is used to describe the self-containeddesktop.

FIG. 29 is a flowchart showing steps taken to initialize the client'sworkstation to use self-contained desktops. Processing commences at 2900whereupon user 2920 is prompted for a user ID and password (step 2910).The user ID and password are received from the user (step 2925). Whenauthenticated, the virtual machine, such as a Java virtual machine(JVM), is loaded on the client operating system platform (step 2930) byJSL. The virtual machine is designed to execute platform-neutral code,such as Java applications. In this manner, the same desktops can bewritten in a platform independent language, such as Java, and executedon a variety of platforms that have implemented the needed virtualmachine.

A Java-based lockdown shell is invoked (step 2940) to provide a desktopenvironment and prevent the user from accessing the underlying operatingsystem being used by the client machine. Desktops that are assigned toboth the workstation and the user are requested from a server (step2945). Server 2950 receives requests and responds by sendingself-contained desktops to the client. The client receives a responsefrom the server (step 2955). The response may be an error or a list ofdesktops.

A determination is made as to whether an error was received from theserver (decision 2960). If an error was received, decision 2960 branchesto “yes” branch 2962 whereupon an error message is displayed on theclient's display device (step 2965) and processing ends at 2995. On theother hand, if an error was not receive, decision 2960 branches to “no”branch 2968 whereupon a determination is made as to whether there areany desktops to display on the client's display device (decision 2970).If there are no desktops display on the client's display device,decision 2970 branches to “yes” branch 2972, the user is informed thatthere are no desktops to displayed (step 2975), and processing ends at2995. On the other hand, if there are desktops assigned to the user andthe workstation, decision 2970 branches to “no” branch 2978 whereuponthe desktops are displayed on the client's display device (predefinedprocess 2980) and processing ends at 2995.

FIG. 30 is a flowchart showing steps taken during client initialization.Processing commences at 3000 whereupon native login code is executed(step 3005). Login data is gathered from the user and sent to the serverfor processing (step 3010). The server sends a response back to theclient which is received at step 3015.

A determination is made as to whether the user was authenticated(decision 3020). If the user was not authenticated, decision 3020branches to “no” branch 3025 whereupon processing ends at 3030. On theother hand, if the user was authenticated, decision 3020 branches to“yes” branch 3035 to continue initialization.

The virtual machine application, such as a Java virtual machine, isinvoked on the client workstation (step 3040). A lockdown process islaunched in the Java environment in order to lock the shell and preventthe user from using the underlying operating system without using theshell environment (step 3045). The server is queried for the desktopshave been assigned to the user/workstation (step 3050). The clientreceives a list of available desktops and compares the listed desktopinformation with desktop data that has already been cached on the clientworkstation (step 3060). Desktops that are included in list but not yetcached on the client workstation are retrieve from the server and cachedon the client workstation (step 3070). The received desktops are storedin client accessible cache 3075. An initial, or default, desktop isselected from the list of available desktops (step 3080). The componentsthat comprise the default desktop are then displayed on the clientdisplay device with other available desktops made available to the userthrough a pop-up window (predefined process 3090, see FIG. 27 forexample of a desktop display). Client initialization processing thenends at 3095.

FIG. 31 is a flowchart showing steps taken during native operatingsystem login. Native operating system login processing commences at 3100whereupon a list of available network domains is displayed to the user(step 3110). A domain is selected from the list by the user (step 3120).A determination is made as to whether to authenticate the client locallyor remotely (decision 3130). If the client is authenticated locally,decision 3130 branches to “yes” branch 3135 whereupon the user isauthenticated at the local machine (step 3140). On the other hand, ifthe user is not authenticated locally, decision 3130 branches to “no”branch 3145 whereupon the user is authenticated on a server to which theclient is connected (step 3150).

A determination is made as to whether the client was authenticated(decision 3160). If the user was not authenticated, decision 3160branches to “no” branch 3165 whereupon an error is displayed on theclient's display device (step 3170) and processing ends at 3195. On theother hand, if the user was authenticated, decision 3160 branches to“yes” branch 3175 whereupon the Java shell launcher is invoked(predefined process 3180, see FIG. 32 for processing details) andprocessing ends at 3195.

FIG. 32 is a flowchart showing steps taken when invoking the Java shelllauncher. Java Shell Launcher execution commences at 3200 whereupon aclass path, or directory, is set (step 3210). The Java virtual machine(JVM) is loaded on the client computing device (step 3220).

A determination is made as to whether the Jshell application is launchedremotely or locally (decision 3230). If the Jshell application islaunched locally, decision 3230 branches to “local” branch 3235whereupon the Jshell application is launched with the user's user ID asa parameter (step 3240). On the other hand, if the Jshell application islaunched remotely, decision 3230 branches to “remote” branch 3245whereupon the Jshell application is launched remotely by providing theserver hostname, the user ID, and the platform ID as parameters (step3250).

After the Jshell application has been launched, JSL enumerates the OSwindow list to find the window corresponding to the Java shell (step3260). The Java shell window is pinned to the bottom of the Z-order listof the operating system windows so that the Java shell window willalways remain in the foreground (step 3270). The Java shell window ismaximized to fit the display screen and all frame controls, such asminimize and resize buttons, are removed from the Java shell window(step 3280). In this manner, the shell application appears as theforeground page on the display and the user is prevented from using theshell page provided by the native operating system platform. Java shelllaunching processing ends at 3295.

FIG. 33A is a screen layout showing an example of a smart graphicalcomponent. The actual container type corresponds to an implementationconstruct such as a class in C++ and Java or a struct in C. Thisimplementation construct will be referred to as the classtype. The smartcomponent attempts to determine the classtype of it's parent component(e.g., a container) at runtime. If the identified classtype is of a typethat the component recognizes, the component modifies its behavior andappearance according to the identified classtype. The behavior andappearance modifications can be programmatically incorporated into thesmart component or read from a configuration file. If the classtype ofthe parent is not recognized, the component may be programmed to ascendit's parent hierarchy until a recognized container is found. In thismanner, the component may be placed inside of a container with anunknown classtype, but if the parent container is itself inside ofanother container with a known classtype, then the component canconfigure itself as if it had been placed directly in the knowncontainer classtype.

The appearance and behavior of the smart component is determined by theclasstype of it's parent container. For example, a smart icon willdisplay a text description if it's parent classtype is a desktop.However, the same smart icon will not display the text description ifit's parent classtype is a toolbar. Furthermore, the smart iconsbehavior may differ depending on the type of parent container. Forexample, if the icond is placed in a toolbar it may be programmed todraw a border around itself when the user places the mouse pointer overit. However, if the same icon is placed on the desktop it may beprogrammed to not display a border when the pointer passes over it. Inaddition, the smart icon may be programmed to execute different coderelated to the component upon activation depending upon the type ofcontainer to which it belongs.

Screen image 3300 includes two examples of a smart graphical componentin the form of a time clock. Time clock 3305 is a component that hasbeen placed in a toolbar container. Time clock 3330 is the samecomponent, but this time the time clock has been placed in the desktopcontainer. The appearance and behavior of the object changes dependingupon the type of parent object, or container, to which the objectbelongs. In the example shown, time clock 3305 is displayed as a digitaltime because of the smaller area available in the parent toolbarcontainer. Conversely, time clock 3330 displays an analog time becauseof the greater area available in the desktop container. In addition,time clock 3330 displays additional information such as the digital timeand date underneath the analog clock image. Furthermore, time clock 3330displays the name of the object (i.e. “clock”) underneath the object.

When the user selects time clock 3305 located in the toolbar, pop-upwindow 3320 is displayed. Pop-up window 3320 displays the day of theweek, date, and has menu items to adjust the time/date and to setnotifications.

FIG. 33B is a screen layout showing an second example of a smartgraphical component. Screen image 3350 is similar to a screen imageshown in FIG. 33A, however in FIG. 33B time clock 3330 has been selectedand pop-up menu 3390 is displayed. The behavior of displayed pop-up menushown in FIG. 33B is different from that shown for the same time clockcomponent shown in FIG. 33A. In particular, in FIG. 33B the user hasdisplay options as to whether a digital time clock, a day of the week,and display date should be shown along with the analog clock. Theseadditional display options are available because of the larger sizeavailable for showing icons in the desktop container, rather than in atoolbar container.

FIG. 34 is a hierarchy chart showing various desktop objects. Desktopobject 3400 is at the top of the hierarchy chart and includes componentobjects 3410 and container objects 3470. Component objects 3410 includeboth visual components 3420 and non-visual components 3440. Visualcomponent objects include icons 3425, folders 3430, and toolbars 3435.Non-visual component objects include application extension code 3445 andapplication definitions 3450. As the name implies, container objects3470 include objects that can include, or hold, other objects. Containerobjects include folders 3480 and toolbars 3490. Visual components suchas icons can be included in container objects.

FIG. 35 is a flowchart showing steps taken in initializing smartgraphical components. Smart graphical component initializationprocessing commences at 3500 whereupon a object oriented parent objectis selected for component (step 3510). The object oriented class typefor the selected parent object is retrieved (step 3520). A determinationis made as to whether the retrieved class type is a recognized classtype, such as a folder or a toolbar (decision 3525). If the retrievedclass type is not recognized, decision 3525 branches to “no” branch 3545whereupon a determination is made as to whether there are more parentsin the object hierarchy (decision 3550). If there are more parents inthe object hierarchy, the parent of the last selected object (i.e. theparent of the last parent, or the grandparent of the subject object) isselected (step 3560) and processing loops back to determine whether thenewly selected parent is a recognized class type. This looping continuesuntil either a recognized class type is found or there are no moreparents in the object hierarchy. If a recognized class type is found,decision 3525 branches to “yes” branch 3530 whereupon the recognizedclass type is selected (step 3540). On the other hand, if there are nomore parents in the object hierarchy, decision 3550 branches to “no”branch 3565 whereupon a default class type is selected for the object(step 3570).

Component appearance data, such as the icon size and other displaycharacteristics, are retrieved along with object behaviorcharacteristics that correspond to the selected class type (step 3575).For example, if the retrieved class type is a toolbar then the icon sizeand display characteristics would be based upon the smaller areaavailable to an icon that is displayed in a toolbar. However, if theretrieved class type is the desktop then the icon size and displaycharacteristics are based upon the larger area available in the desktop.

The component is displayed using the retrieved appearance data thatcorresponds to the class type. The system waits for the component to beinvoked (step 3585, i.e. until the component is selected by the user).When the component is invoked, the component is executed using behaviorattributes that correspond to the class type (step 3590).

FIG. 36 is a flowchart showing steps taken in processing displayattributes for smart graphical components. Smart desktop processingcommences at 3600 whereupon a determination is made as to whether theclass type is a toolbar (decision 3605). If the class type is a toolbar,decision 3605 branches to “yes” branch 3610 whereupon the toolbar iconfor the component is retrieved and displayed in the toolbar (step 3615),a border is drawn around the icon in the toolbar (step 3620), andprocessing ends at 3625.

If the class type is not a toolbar, decision 3605 branches to “no”branch 3630 whereupon a determination is made as to whether the classtype is a folder (decision 3635). If the class type is a folder,decision 3635 branches to “yes” branch 3640 whereupon the folder iconfor the component is retrieved and displayed in the folder (step 3645),a short component description is displayed underneath the icon (step3650), and processing ends at 3655.

If the class type is not a toolbar or a folder, decision 3635 branchesto “no” branch 3660 whereupon a determination is made as to whether theclass type is the desktop (decision 3665). If the class type is thedesktop, decision 3665 branches to “yes” branch 3668 whereupon thelarger icon is retrieved in displayed on the desktop (step 3670), alonger component description is displayed under the icon (decision3675), and processing ends at 3680.

If the class type is not a toolbar, a folder, or desktop, then decision3665 branches to “no” branch 3682 whereupon a default icon is retrievedand displayed (step 3685), other default display characteristics areretrieved and applied to the icon (step 3690), and processing ends at3695.

FIG. 37 is a flowchart showing steps taken in processing behaviorattributes for smart graphical components. Smart desktop processingcommences at 3700 whereupon a determination is made as to whether theinvoked component has a parent with a toolbar class type (decision3705). If the invoked component has a toolbar parent class type,decision 3705 branches to “yes” branch 3710 whereupon the component'stoolbar behavior is retrieved (step 3715), the retrieved toolbarbehavior is executed (step 3720), and processing ends at 3725.

If the invoked component does not have a parent with a toolbar classtype, decision 3705 branches to “no” branch 3730 whereupon adetermination is made as to whether the invoked component has a parentwith a folder class type (decision 3735). If the invoked component has afolder parent class type, decision 3735 branches to “yes” branch 3740whereupon the component's folder behavior is retrieved (step 3745),executed (step 3750), and processing ends at 3755.

If the invoked component does not have any parent with a toolbar orfolder class type, decision 3735 branches to “no” branch 3760 whereupona determination is made as to whether the invoked component has a parentwith a desktop class type (decision 3765). If the invoked component hasa desktop parent class type, decision 3765 branches to “yes” branch 3768whereupon the component's desktop behavior is retrieved (step 3770),executed (step 3775), and processing ends at step 3780.

If the invoked component does not have a parent with a class type oftoolbar, folder, or desktop, decision 3765 branches to “no” branch 3782whereupon the components default behavior is retrieved (step 3785),executed (step 3790), and processing ends at step 3795.

FIG. 38 illustrates information handling system 3801 which is asimplified example of a computer system capable of performing theoperations described herein. Computer system 3801 includes processor3800 which is coupled to host bus 3805. A level two (L2) cache memory3810 is also coupled to the host bus 3805. Host-to-PCI bridge 3815 iscoupled to main memory 3820, includes cache memory and main memorycontrol functions, and provides bus control to handle transfers amongPCI bus 3825, processor 3800, L2 cache 3810, main memory 3820, and hostbus 3805. PCI bus 3825 provides an interface for a variety of devicesincluding, for example, LAN card 3830. PCI-to-ISA bridge 3835 providesbus control to handle transfers between PCI bus 3825 and ISA bus 3840,universal serial bus (USB) functionality 3845, IDE device functionality3850, power management functionality 3855, and can include otherfunctional elements not shown, such as a real-time clock (RTC), DMAcontrol, interrupt support, and system management bus support.Peripheral devices and input/output (I/O) devices can be attached tovarious interfaces 3860 (e.g., parallel interface 3862, serial interface3864, infrared (IR) interface 3866, keyboard interface 3868, mouseinterface 3870, fixed disk (HDD) 3872 coupled to ISA bus 3840.Alternatively, many I/O devices can be accommodated by a super I/Ocontroller (not shown) attached to ISA bus 3840.

BIOS 3880 is coupled to ISA bus 3840, and incorporates the necessaryprocessor executable code for a variety of low-level system functionsand system boot functions. BIOS 3880 can be stored in any computerreadable medium, including magnetic storage media, optical storagemedia, flash memory, random access memory, read only memory, andcommunications media conveying signals encoding the instructions (e.g.,signals from a network). In order to attach computer system 3801 toanother computer system to copy files over a network, LAN card 3830 iscoupled to PCI bus 3825 and to PCI-to-ISA bridge 3835. Similarly, toconnect computer system 3801 to an ISP to connect to the Internet usinga telephone line connection, modem 3875 is connected to serial port 3864and PCI-to-ISA Bridge 3835.

While the computer system described in FIG. 38 is capable of executingthe invention described herein, this computer system is simply oneexample of a computer system. Those skilled in the art will appreciatethat many other computer system designs are capable of performing theinvention described herein.

One of the preferred implementations of the invention is an application,namely, a set of instructions (program code) in a code module which may,for example, be resident in the random access memory of the computer.Until required by the computer, the set of instructions may be stored inanother computer memory, for example, on a hard disk drive, or inremovable storage such as an optical disk (for eventual use in a CD ROM)or floppy disk (for eventual use in a floppy disk drive), or downloadedvia the Internet or other computer network. Thus, the present inventionmay be implemented as a computer program product for use in a computer.In addition, although the various methods described are convenientlyimplemented in a general purpose computer selectively activated orreconfigured by software, one of ordinary skill in the art would alsorecognize that such methods may be carried out in hardware, in firmware,or in more specialized apparatus constructed to perform the requiredmethod steps.

While particular embodiments of the present invention have been shownand described, it will be obvious to those skilled in the art that,based upon the teachings herein, changes and modifications may be madewithout departing from this invention and its broader aspects and,therefore, the appended claims are to encompass within their scope allsuch changes and modifications as are within the true spirit and scopeof this invention. Furthermore, it is to be understood that theinvention is solely defined by the appended claims. It will beunderstood by those with skill in the art that if a specific number ofan introduced claim element is intended, such intent will be explicitlyrecited in the claim, and in the absence of such recitation no suchlimitation is present. For a non-limiting example, as an aid tounderstanding, the following appended claims contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimelements. However, the use of such phrases should not be construed toimply that the introduction of a claim element by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim element to inventions containing only one such element,even when the same claim includes the introductory phrases “one or more”or “at least one” and indefinite articles such as “a” or “an”; the sameholds true for the use in the claims of definite articles.

1. (canceled)
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. (canceled) 6.(canceled)
 7. (canceled)
 8. (canceled)
 9. (canceled)
 10. (canceled) 11.(canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)
 15. (canceled)16. (canceled)
 17. (canceled)
 18. (canceled)
 19. (canceled) 20.(canceled)
 21. (canceled)
 22. (canceled)
 23. (canceled)
 24. (canceled)25. A method of executing a container-aware graphical component on aninformation handling system, comprising: executing, by one or moreprocessors, an operating system for managing the information handlingsystem; executing a virtual machine middleware application on theoperating system; and executing an object handling tool, the objecthandling tool further executing a graphical component by performing thefollowing: identifying a classtype of a parent object corresponding tothe graphical component; retrieving one or more display attributes andone or more behavior attributes based on the identified classtype;displaying, based upon the display attributes, a graphical imagecorresponding to the graphical component on a display device accessibleby the one or more processors; receiving a request for the graphicalcomponent; and executing, in response to the request, a program codeselected from a plurality of program codes, the selection based upon thebehavior attributes.
 26. The method as described in claim 25 wherein theidentifying further comprises: retrieving a first classtypecorresponding to a first parent object, the first parent object beingthe immediate parent of the graphical component; determining whether thefirst classtype is a recognized container class; retrieving, in responseto the first classtype not being a recognized container class, a secondclasstype corresponding to a second parent object, the second parentobject being a parent of the first parent object; determining whetherthe second classtype is a recognized container class; and assigning theclasstype in response to the second classtype being a recognizedcontainer class.
 27. The method as described in claim 25 furthercomprising: traversing, from the graphical component, up an object treeof parent objects until a parent classtype corresponding to one of theparent objects is a recognized container class; and assigning theclasstype to the parent classtype that first matches a recognizedcontainer class.
 28. The method as described in claim 25 wherein theparent classtype corresponds to a container, wherein the container isselected from the group consisting of a toolbar, a desktop, a folder, awindow, a frame, a dialog box, and a menu.
 29. The method as describedin claim 25 wherein at least one of the display attributes is selectedfrom the group consisting of a textual description, an icon size, anicon border, and an icon highlight.
 30. The method as described in claim25 wherein the graphical component is adapted to be displayed andexecuted on a plurality of operating system platforms, and wherein thedisplaying the graphical image and the executing the program code areconsistent across the plurality of operating system platforms.
 31. Themethod as described in claim 25 further comprising: loading the virtualmachine middleware application on the operating system, wherein thevirtual machine middleware application is adapted to runplatform-neutral applications; invoking a desktop shell application inthe virtual machine middleware application, the desktop shell includinga desktop window that includes one or more container windows; andreceiving the graphical component from a server connected to theinformation handling system over a computer network, wherein thedisplaying the graphical image is performed within the desktop windowand wherein the executing the program code is performed by the virtualmachine middleware application.
 32. The method as described in claim 31wherein the virtual machine middleware application is a Java virtualmachine and wherein both the desktop shell application and the graphicalcomponent are Java applications.
 33. A computer program product storedon a computer operable media, the computer operable media containinginstructions for execution by a computer, which, when executed by thecomputer, cause the computer to execute a method for executing acontainer-aware graphical object, the method comprising: executing, byone or more processors, an operating system for managing an informationhandling system; executing a virtual machine middleware application onthe operating system; and executing an object handling tool, the objecthandling tool further executing a graphical component by performing thefollowing: identifying a classtype of a parent object corresponding tothe graphical component; retrieving one or more display attributes andone or more behavior attributes based on the identified classtype;displaying, based upon the display attributes, a graphical imagecorresponding to the graphical component on a display device accessibleby the one or more processors; receiving a request for the graphicalcomponent; and executing, in response to the request, a program codeselected from a plurality of program codes, the selection based upon thebehavior attributes.
 34. The computer program product as described inclaim 33 wherein the identifying further comprises: retrieving a firstclasstype corresponding to a first parent object, the first parentobject being the immediate parent of the graphical component;determining whether the first classtype is a recognized container class;retrieving, in response to the first classtype not being a recognizedcontainer class, a second classtype corresponding to a second parentobject, the second parent object being a parent of the first parentobject; determining whether the second classtype is a recognizedcontainer class; and assigning the classtype in response to the secondclasstype being a recognized container class.
 35. The computer programproduct as described in claim 33, the method further comprising:traversing, from the graphical component, up an object tree of parentobjects until a parent classtype corresponding to one of the parentobjects is a recognized container class; and assigning the classtype tothe parent classtype that first matches a recognized container class.36. The computer program product as described in claim 33 wherein theparent classtype corresponds to a container, wherein the container isselected from the group consisting of a toolbar, a desktop, a folder, awindow, a frame, a dialog box, and a menu.
 37. The computer programproduct as described in claim 33 wherein at least one of the displayattributes is selected from the group consisting of a textualdescription, an icon size, an icon border, and an icon highlight. 38.The computer program product as described in claim 33 wherein thegraphical component is adapted to be displayed and executed on aplurality of operating system platforms, and wherein the displaying thegraphical image and the executing the program code are consistent acrossthe plurality of operating system platforms.
 39. The computer programproduct as described in claim 33, the method further comprising: loadingthe virtual machine middleware application on the operating system,wherein the virtual machine middleware application is adapted to runplatform-neutral applications; invoking a desktop shell application inthe virtual machine middleware application, the desktop shell includinga desktop window that includes one or more container windows; andreceiving the graphical component from a server connected to theinformation handling system over a computer network, wherein thedisplaying the graphical image is performed within the desktop windowand wherein the executing the program code is performed by the virtualmachine middleware application.
 40. The computer program product asdescribed in claim 39 wherein the virtual machine middleware applicationis a Java virtual machine and wherein both the desktop shell applicationand the graphical component are Java applications.